Skip to content

KEP-3314: adding beta PRR documentation#5877

Merged
k8s-ci-robot merged 1 commit intokubernetes:masterfrom
carlbraganza:kep3314-beta
Feb 11, 2026
Merged

KEP-3314: adding beta PRR documentation#5877
k8s-ci-robot merged 1 commit intokubernetes:masterfrom
carlbraganza:kep3314-beta

Conversation

@carlbraganza
Copy link
Contributor

@carlbraganza carlbraganza commented Feb 2, 2026

  • One-line PR description: Update KEP-3314 PRR for Beta.
  • Other comments:

@k8s-ci-robot k8s-ci-robot added the kind/kep Categorizes KEP tracking issues and PRs modifying the KEP directory label Feb 2, 2026
@k8s-ci-robot k8s-ci-robot requested a review from saad-ali February 2, 2026 21:41
@k8s-ci-robot k8s-ci-robot added the sig/storage Categorizes an issue or PR as relevant to SIG Storage. label Feb 2, 2026
@k8s-ci-robot k8s-ci-robot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Feb 2, 2026
@k8s-ci-robot
Copy link
Contributor

Hi @carlbraganza. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Feb 2, 2026
@xing-yang
Copy link
Contributor

/ok-to-test

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Feb 2, 2026
@carlbraganza carlbraganza force-pushed the kep3314-beta branch 4 times, most recently from 6f475d4 to 943a783 Compare February 3, 2026 16:35
@xing-yang
Copy link
Contributor

General comment: Please provide more details when you say "CSI driver specific."

For e2e tests, please include links to the test files.

@k8s-ci-robot k8s-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Feb 3, 2026
Copy link
Member

@stlaz stlaz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PRR shadow review

installed by the CSI driver, or by
reinstalling the CSI driver without this feature enabled.

It can also be effectively disabled by modifying the CSI driver specific
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You would still likely have at least one cluster-admin in the cluster that could still use it. I wouldn't say this is a valid way to disable the feature.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, I'll remove this.

Copy link
Contributor Author

@carlbraganza carlbraganza left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@stlaz I hope I've addressed all your feedback.

installed by the CSI driver, or by
reinstalling the CSI driver without this feature enabled.

It can also be effectively disabled by modifying the CSI driver specific
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, I'll remove this.

[TokenReview](https://kubernetes.io/docs/reference/kubernetes-api/authentication-resources/token-review-v1/) and
[SubjectAccessReview](https://kubernetes.io/docs/reference/kubernetes-api/authorization-resources/subject-access-review-v1/)
APIs are controlled by Kubernetes security policy.
A side effect of the use of these APIs is that it partially mitigates
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kubernetes/sig-auth-proposals This KEP suggests that an unauthenticated client can cause N authenticated clients to fan out requests to the KAS until KAS starts rate-limiting each of these authenticated clients. N is the number of CSI driver instances installed in the cluster.

Is this ok?

Comment on lines 1134 to 1147
No integration tests are required. This feature is better tested with e2e tests.
[Integration tests](https://github.com/kubernetes-csi/external-snapshot-metadata/blob/main/.github/workflows/integration-test.yaml)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Permanent link, please.

Why is this considered an integration test?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we point to actual testing code, not the workflow that runs them?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that is because its run as part of the CI steps. Its scope is beyond that of a unit test.

I've changed the link to a permanent link.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that is because its run as part of the CI steps. Its scope is beyond that of a unit test.

Yes, but the way these tests work actually makes them e2e tests, not integration tests. You're testing an actual user scenario from start to finish, rather than observing how certain units interact with each other in a simulated/isolated environment.

When you actually need a running kube cluster for a test, you're not very likely to be doing integration testing.

block mode backups should become more efficient in both storage
space and time utilization.
The `GetMetadataAllocated` and `GetMetadataDelta` snapshot metadata operations
should be successful most of time.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Define "most of the time" with a specific number.

Copy link
Contributor Author

@carlbraganza carlbraganza Feb 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have no basis on which to propose a number. Given that nothing is 100% successful, I reworded this in relative terms:

The GetMetadataAllocated and GetMetadataDelta snapshot metadata operations
should be as successful as an existing CreateSnapshot CSI operation on the
same volume, assuming that sufficient cluster resources are available for the
duration of the operation.

@k8s-ci-robot k8s-ci-robot added sig/auth Categorizes an issue or PR as relevant to SIG Auth. kind/design Categorizes issue or PR as related to design. labels Feb 9, 2026
@enj enj moved this to Needs Triage in SIG Auth Feb 9, 2026
@enj enj added this to SIG Auth Feb 9, 2026
Copy link
Contributor

@soltysh soltysh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few more questions from PRR

Comment on lines 1134 to 1147
No integration tests are required. This feature is better tested with e2e tests.
[Integration tests](https://github.com/kubernetes-csi/external-snapshot-metadata/blob/main/.github/workflows/integration-test.yaml)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we point to actual testing code, not the workflow that runs them?

We expect no non-infra related flakes in the last month as a GA graduation criteria.
-->

Link: [SnapshotMetadata E2E test PR](https://github.com/kubernetes/kubernetes/pull/130918)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These tests are part of alpha requirements, and they are NOT merged yet. So how are you planning to deliver beta?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are there others, can you link them here?

Copy link
Contributor Author

@carlbraganza carlbraganza Feb 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we point to actual testing code, not the workflow that runs them?

I changed the text to read:

Integration tests are built into the build process. The test is based on the CSI Hostpath driver and uses the snapshot-metadata-lister and snapshot-metadata-verifier commands built by in the external-snapshot-metadata repository, yq, kubectl and other standard Linux utilities. See the workflow script for test details.

These tests are part of alpha requirements, and they are NOT merged yet. So how are you planning to deliver beta?

Others are working on getting this merged ASAP.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These tests are part of alpha requirements, and they are NOT merged yet. So how are you planning to deliver beta?

I see the linked PR is tagged for merge, that's a bit better.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

feature-gates:
- name:
components:
disable-supported: true
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you put here information, that this is separate component. I keep forgetting that and need to look in other places for this.

Copy link
Contributor

@soltysh soltysh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve
the PRR section

We expect no non-infra related flakes in the last month as a GA graduation criteria.
-->

Link: [SnapshotMetadata E2E test PR](https://github.com/kubernetes/kubernetes/pull/130918)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These tests are part of alpha requirements, and they are NOT merged yet. So how are you planning to deliver beta?

I see the linked PR is tagged for merge, that's a bit better.

@github-project-automation github-project-automation bot moved this from Needs Triage to In Review in SIG Auth Feb 11, 2026
@xing-yang
Copy link
Contributor

Test PR kubernetes/kubernetes#130918 is merged.
Please submit a followup PR to replace it with a link to the merged test file: https://github.com/kubernetes/kubernetes/blob/master/test/e2e/storage/testsuites/snapshot-metadata.go

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Feb 11, 2026
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: carlbraganza, soltysh, xing-yang

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 11, 2026
@k8s-ci-robot k8s-ci-robot merged commit 7d9b02e into kubernetes:master Feb 11, 2026
4 checks passed
@k8s-ci-robot k8s-ci-robot added this to the v1.36 milestone Feb 11, 2026
@github-project-automation github-project-automation bot moved this from In Review to Closed / Done in SIG Auth Feb 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/design Categorizes issue or PR as related to design. kind/kep Categorizes KEP tracking issues and PRs modifying the KEP directory lgtm "Looks good to me", indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. sig/auth Categorizes an issue or PR as relevant to SIG Auth. sig/storage Categorizes an issue or PR as relevant to SIG Storage. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

Status: Closed / Done

Development

Successfully merging this pull request may close these issues.

5 participants